Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VMware Enterprise PKS upgrade failed with error : Stopping services '[nsx-kube-proxy]' errored (74787)

Last Updated: 9/19/2019Categories: TroubleshootingTotal Views: 1770Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When you are upgrading the VMware Enterprise PKS, it failed with the error similar to:
Stopping Monitored Services: Stopping services '[nsx-kube-proxy]' errored

In the bosh task for the upgrade activity, you see the entries similar to:
Task 88758 | 14:45:49 | Updating instance master: master/859bc553-1a49-4a98-aeb1-e6d51cb6667e (2) (00:03:50)
Task 88758 | 14:49:39 | Updating instance worker: worker/68f419aa-d3fe-4578-84ed-49510950bd3e (0) (canary) (00:00:50)
L Error: Action Failed get_task: Task 1c51928e-13cd-44cb-720e-842c87b3d114 result: Stopping Monitored Services: Stopping services '[nsx-kube-proxy]' errored
Task 88758 | 14:50:29 | Error: Action Failed get_task: Task 1c51928e-13cd-44cb-720e-842c87b3d114 result: Stopping Monitored Services: Stopping services '[nsx-kube-proxy]' errored

In the /var/vcap/sys/log/kube-proxy/nsx-kube-proxy.stdout.log on worker node, you see the entries similar to:
2019-02-21T12:31:40.317Z 6a2de506-a28e-4f82-81b3-ea3e1ca76458 NSX 13197 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_kube_proxy" level="ERROR" errorCode="NCP02002"] nsx_ujo.k8s.proxy.proxy Failed to execute command: <nsx_ujo.k8s.proxy.proxy.OVSFlowBuildCommand object at 0x7fcbdca53d90>
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/nsx_ujo/k8s/proxy/proxy.py", line 342, in command_execution_loop
cmd.execute()
File "/usr/local/lib/python2.7/dist-packages/nsx_ujo/k8s/proxy/proxy.py", line 333, in execute
utils.call_popen_with_privsep(shlex.split(cmd))
File "/usr/local/lib/python2.7/dist-packages/oslo_privsep/priv_context.py", line 207, in _wrap
return self.channel.remote_call(name, args, kwargs)
File "/usr/local/lib/python2.7/dist-packages/oslo_privsep/daemon.py", line 202, in remote_call
raise exc_type(*result[2])
RuntimeError: Fatal error executing ovs-ofctl -O OpenFlow13 del-flows nsx-container cookie=7/-1
1 2019-02-21T12:31:40.317Z 6a2de506-a28e-4f82-81b3-ea3e1ca76458 NSX 13197 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_kube_proxy" level="INFO"] nsx_ujo.k8s.proxy.proxy Creating OVS flow rebuild commands
1 2019-02-21T12:31:40.320Z 6a2de506-a28e-4f82-81b3-ea3e1ca76458 NSX 13197 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_kube_proxy" level="WARNING"] oslo.privsep.daemon privsep log: ovs-ofctl: nsx-container is not a bridge or a socket
1 2019-02-21T12:31:40.320Z 6a2de506-a28e-4f82-81b3-ea3e1ca76458 NSX 13197 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_kube_proxy" level="ERROR" errorCode="NCP02003"] nsx_ujo.k8s.proxy.proxy OVS flow check failed: Fatal error executing ovs-ofctl -O OpenFlow13 dump-flows nsx-container

In the /var/vcap/jobs/nsx-kube-proxy logs, you see that kube-proxy exiting:
1 2019-04-22T22:19:50.234Z d0c11156-0968-44ce-9232-ac2e02f7b3e5 NSX 27711 - [nsx@6876 comp="nsx-container-node" subcomp="nsx_kube_proxy" level="INFO"] nsx_ujo.k8s.proxy.proxy nsx_kube_proxy exiting...

Cause

The issue occurs because nsx-kube-proxy is not able to stop on the worker node.

Resolution

This is a known issue with NSX Container Plugin(NCP) 2.5.0 and earlier. it will be resolved in future release.

Workaround

To workaround the issue, try restarting the nsx-kube-proxy process on worker node and retry the upgrade.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
应用热修补程序后，Usage Meter 无法导出日志包并发送未加密的报告 (74693)

KB
•
/var/log パーティションが VMware NSX-T コントローラ ノードでローテーションせずに急激に増大する (74758)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware PKS

Related Versions:

VMware PKS 1.x

Take Our Survey

Support Assistant